Add 2026 Q2 Best Practices WG quarterly report#598
Open
balteravishay wants to merge 6 commits into
Open
Conversation
gkunz
reviewed
Apr 13, 2026
lehors
reviewed
Apr 14, 2026
lehors
reviewed
Apr 14, 2026
|
|
||
| #### Current Status | ||
|
|
||
| * Integrated baseline criteria (levels 1–3) into the badge system. Projects can now complete forms and earn baseline badges, with a transition period ending 2026-06-01 for enforcing new criteria. |
Contributor
There was a problem hiding this comment.
Are there 2 different badges? A baseline one and a best practices one?
Contributor
There was a problem hiding this comment.
The two different badges have 2 different URLs.
lehors
reviewed
Apr 14, 2026
lehors
reviewed
Apr 14, 2026
lehors
reviewed
Apr 14, 2026
lehors
reviewed
Apr 14, 2026
steiza
approved these changes
Apr 14, 2026
Signed-off-by: balteravishay <avishay.balter@gmail.com>
Co-authored-by: Georg Kunz <georg.kunz@ericsson.com> Signed-off-by: Avishay Balter <avishay.balter@gmail.com> Signed-off-by: balteravishay <avishay.balter@gmail.com>
Co-authored-by: Georg Kunz <georg.kunz@ericsson.com> Signed-off-by: Avishay Balter <avishay.balter@gmail.com> Signed-off-by: balteravishay <avishay.balter@gmail.com>
Signed-off-by: balteravishay <avishay.balter@gmail.com>
a9b6131 to
3056a0c
Compare
Contributor
|
Oh, one more comment: FYI, we have added to the TI report template a question about Funding requests. |
Signed-off-by: balteravishay <avishay.balter@gmail.com>
bobcallaway
approved these changes
Apr 14, 2026
gkunz
approved these changes
May 13, 2026
gkunz
reviewed
May 13, 2026
|
|
||
| * Continue working on a threat modelling [guide for web developers](https://github.com/mdn/content/pull/42980). | ||
|
|
||
| ## Questions/Issues for the TAC |
Contributor
There was a problem hiding this comment.
To @lehors' comment about the missing information regarding funding:
Suggested change
| ## Questions/Issues for the TAC | |
| ## Funding requests and updates | |
| The WG briefly discussed applying for funding of a technical writer to support the group with reviewing, finalizing, and maintaining the various guides we host. However, there currently no concrete funding request in the pipeline. | |
| The WG currently does not receive funding yet. | |
| ## Questions/Issues for the TAC |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request adds the 2026 Q2 report for the Best Practices Working Group. Major updates include launching Baseline badges, first release of the Python Secure Coding Guide and publishing the W3C web security guidelines draft.